Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: fb246f6b60edcd46fe1f97247393bdd8a8e143f7ddf9bf3840554f0038c03d94

Tx prefix hash: 38a8b396bfbc46f0dfd9ae521d99016494c97862ffd2da335bcdae732e8b90de
Tx public key: b4ec814f9e8d5bdb1fe2cdf2816a8b58e0c6ff891bd48caf1782bf0dcb32882b
Timestamp: 1707579967 Timestamp [UCT]: 2024-02-10 15:46:07 Age [y:d:h:m:s]: 01:271:18:09:04
Block: 954579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 452997 RingCT/type: yes/0
Extra: 01b4ec814f9e8d5bdb1fe2cdf2816a8b58e0c6ff891bd48caf1782bf0dcb32882b02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0eeef7e7508e03e1f48d06f2bf45e7f29c4c402440e600fc41f1d0a9214bfce 0.600000000000 1413859 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 954589, "vin": [ { "gen": { "height": 954579 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0eeef7e7508e03e1f48d06f2bf45e7f29c4c402440e600fc41f1d0a9214bfce" } } ], "extra": [ 1, 180, 236, 129, 79, 158, 141, 91, 219, 31, 226, 205, 242, 129, 106, 139, 88, 224, 198, 255, 137, 27, 212, 140, 175, 23, 130, 191, 13, 203, 50, 136, 43, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8