Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de38951c40b5004a69a6a0003eb17e44f755a1625a5a90d6c23c22f3174e2dc1

Tx prefix hash: 06ff06d4834709a8cc42f938bf2edd46578cd77fb8e736a7b2bf4806bd9cc319
Tx public key: 6760bb6399d7a4d01df296c0f38d4a7f4bec56704108881e522678b2882e8172
Timestamp: 1672072816 Timestamp [UCT]: 2022-12-26 16:40:16 Age [y:d:h:m:s]: 02:092:16:33:25
Block: 661095 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 587924 RingCT/type: yes/0
Extra: 016760bb6399d7a4d01df296c0f38d4a7f4bec56704108881e522678b2882e817202110000000433af99f4000000000000000000

1 output(s) for total of 3.958382899000 dcy

stealth address amount amount idx
00: bbc5ecae4ac2a01eded9d56d94c638df022efb0d1ebd6fe629c8185035e14c4e 3.958382899000 1101850 of 0

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": 661105, "vin": [ { "gen": { "height": 661095 } } ], "vout": [ { "amount": 3958382899, "target": { "key": "bbc5ecae4ac2a01eded9d56d94c638df022efb0d1ebd6fe629c8185035e14c4e" } } ], "extra": [ 1, 103, 96, 187, 99, 153, 215, 164, 208, 29, 242, 150, 192, 243, 141, 74, 127, 75, 236, 86, 112, 65, 8, 136, 30, 82, 38, 120, 178, 136, 46, 129, 114, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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