Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5cfb19103c0952cc9f970356b42b3f488a325eb867f487a80d1733dd2f2d3bc0

Tx prefix hash: 52f3b72b4022b69d93b7b8a5fcbaa53ecfd75b6fe5f14c36e236a71bf398914e
Tx public key: 54cb02c340a78d632de97478e92a1d348b3c5b181b052c802fc4d03d3b8bca8f
Timestamp: 1713191373 Timestamp [UCT]: 2024-04-15 14:29:33 Age [y:d:h:m:s]: 01:039:10:05:43
Block: 1001099 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289165 RingCT/type: yes/0
Extra: 0154cb02c340a78d632de97478e92a1d348b3c5b181b052c802fc4d03d3b8bca8f02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8a68a48a4c8ee8b3847f09628766d3ca2545b3d3e9c088b409e02f5460e1346 0.600000000000 1461601 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": 1001109, "vin": [ { "gen": { "height": 1001099 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8a68a48a4c8ee8b3847f09628766d3ca2545b3d3e9c088b409e02f5460e1346" } } ], "extra": [ 1, 84, 203, 2, 195, 64, 167, 141, 99, 45, 233, 116, 120, 233, 42, 29, 52, 139, 60, 91, 24, 27, 5, 44, 128, 47, 196, 208, 61, 59, 139, 202, 143, 2, 17, 0, 0, 0, 6, 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