Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4a70fe69dc5c038f748b9dd1ff9c1100f7431a1e36a8f90ba36c1449e9d4ff7

Tx prefix hash: fbc3a2f7d2abbbad867618da6cd44e84b924895baaeb0295e3374c996b824980
Tx public key: 22b372a8352b3e8375cc83e51b324f06a10a3c95f711a692aaa8f65961c0cc37
Timestamp: 1736812536 Timestamp [UCT]: 2025-01-13 23:55:36 Age [y:d:h:m:s]: 00:059:12:42:33
Block: 1196795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42337 RingCT/type: yes/0
Extra: 0122b372a8352b3e8375cc83e51b324f06a10a3c95f711a692aaa8f65961c0cc37021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43f5eae0f5c99f74930058d5326bd220104e878d6a1a6ecf84deb80072547ae2 0.600000000000 1683398 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": 1196805, "vin": [ { "gen": { "height": 1196795 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43f5eae0f5c99f74930058d5326bd220104e878d6a1a6ecf84deb80072547ae2" } } ], "extra": [ 1, 34, 179, 114, 168, 53, 43, 62, 131, 117, 204, 131, 229, 27, 50, 79, 6, 161, 10, 60, 149, 247, 17, 166, 146, 170, 168, 246, 89, 97, 192, 204, 55, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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