Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47c2a10f485c3fc3d525e0c03e9b09b08f294729637f183250ee2abb92927e5b

Tx prefix hash: 9c84417521f910946dc0a45200e554e7856a8ec21852d25da9859cdcdd520571
Tx public key: 027b1fdad1631df8223184ab0e54071f25ef5b7430bd6f36cd253e71af4980bb
Timestamp: 1713224936 Timestamp [UCT]: 2024-04-15 23:48:56 Age [y:d:h:m:s]: 00:355:03:37:49
Block: 1001368 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253910 RingCT/type: yes/0
Extra: 01027b1fdad1631df8223184ab0e54071f25ef5b7430bd6f36cd253e71af4980bb02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c277cbe71d4569aa89b0e9fb7ef3ee4ed033cef83aac9937039c6624870b245 0.600000000000 1461872 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": 1001378, "vin": [ { "gen": { "height": 1001368 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c277cbe71d4569aa89b0e9fb7ef3ee4ed033cef83aac9937039c6624870b245" } } ], "extra": [ 1, 2, 123, 31, 218, 209, 99, 29, 248, 34, 49, 132, 171, 14, 84, 7, 31, 37, 239, 91, 116, 48, 189, 111, 54, 205, 37, 62, 113, 175, 73, 128, 187, 2, 17, 0, 0, 0, 2, 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