Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 194eab72de5cb1d4f1bdc569085dbb86f7aeee74dd6fe83e65e43b1b7cf9cbd1

Tx prefix hash: 163300d4042ab5377c9274a943905ad64d8940bc52bfb4cc2535317b7f5b905c
Tx public key: 7df2bf15bfa1c3b902ddd4e9c49fdfa49f3079242260ca73509a730eb37da097
Timestamp: 1711100098 Timestamp [UCT]: 2024-03-22 09:34:58 Age [y:d:h:m:s]: 00:358:10:11:49
Block: 983792 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256263 RingCT/type: yes/0
Extra: 017df2bf15bfa1c3b902ddd4e9c49fdfa49f3079242260ca73509a730eb37da0970211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a0d4f7144b412ed60c1a9dcc2d20f4cf76cbfbec8e90bb11de5c28cd7fec4db 0.600000000000 1443939 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": 983802, "vin": [ { "gen": { "height": 983792 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a0d4f7144b412ed60c1a9dcc2d20f4cf76cbfbec8e90bb11de5c28cd7fec4db" } } ], "extra": [ 1, 125, 242, 191, 21, 191, 161, 195, 185, 2, 221, 212, 233, 196, 159, 223, 164, 159, 48, 121, 36, 34, 96, 202, 115, 80, 154, 115, 14, 179, 125, 160, 151, 2, 17, 0, 0, 0, 9, 0, 17, 5, 91, 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