Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb6fe36b094a28aa2eff903ab78e75f285963a9f30be4d0907a057809ac0a7cb

Tx prefix hash: ba956112e08a877f6b6cc1e913b29782951c3acd0d05bbf294f4a285f5404cdf
Tx public key: 8c4f2cba21a8f614d6c062fd33b3a57e9f5d425495dd151fef69b9bfadc121ef
Timestamp: 1707034673 Timestamp [UCT]: 2024-02-04 08:17:53 Age [y:d:h:m:s]: 01:064:05:19:57
Block: 950059 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306952 RingCT/type: yes/0
Extra: 018c4f2cba21a8f614d6c062fd33b3a57e9f5d425495dd151fef69b9bfadc121ef02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4550a3d80d8bba4631099de80a6bad3e2814f6a005c10b7c9847705c7c87d33e 0.600000000000 1408617 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": 950069, "vin": [ { "gen": { "height": 950059 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4550a3d80d8bba4631099de80a6bad3e2814f6a005c10b7c9847705c7c87d33e" } } ], "extra": [ 1, 140, 79, 44, 186, 33, 168, 246, 20, 214, 192, 98, 253, 51, 179, 165, 126, 159, 93, 66, 84, 149, 221, 21, 31, 239, 105, 185, 191, 173, 193, 33, 239, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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