Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88ed21d933cf8b76c96bb14eac589fb278207ae93b53a43184245c1ef7c77d61

Tx prefix hash: 26bd53bd0a0087d5a4320a8febeb616966e64ed9737d52e4da4ce171bbec38b4
Tx public key: 832e8a3e0bb75308f3c0120d10a74ca6c67bbaf1a21233a9d5547af8b79b3d72
Timestamp: 1717810799 Timestamp [UCT]: 2024-06-08 01:39:59 Age [y:d:h:m:s]: 00:169:06:06:28
Block: 1039408 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121140 RingCT/type: yes/0
Extra: 01832e8a3e0bb75308f3c0120d10a74ca6c67bbaf1a21233a9d5547af8b79b3d7202110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9af8733b74253e007e1749537eda3f00e77dbb8d6b790a22e74584d25f7b16c 0.600000000000 1508047 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": 1039418, "vin": [ { "gen": { "height": 1039408 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9af8733b74253e007e1749537eda3f00e77dbb8d6b790a22e74584d25f7b16c" } } ], "extra": [ 1, 131, 46, 138, 62, 11, 183, 83, 8, 243, 192, 18, 13, 16, 167, 76, 166, 198, 123, 186, 241, 162, 18, 51, 169, 213, 84, 122, 248, 183, 155, 61, 114, 2, 17, 0, 0, 0, 4, 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