Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5881f1ccce7ae2a5712ea9744cc524b815c4d3f35348b1cb2d022be16a182973

Tx prefix hash: be74938fe4ab53adae9cf8f62868b89c2e66f85a28b2649f5282435e14bfadcc
Tx public key: 45ae4019acd91c736bae6e37f6f3895d674d89d40517f971615a1fadee091bfe
Timestamp: 1723230898 Timestamp [UCT]: 2024-08-09 19:14:58 Age [y:d:h:m:s]: 00:225:14:37:50
Block: 1084340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161130 RingCT/type: yes/0
Extra: 0145ae4019acd91c736bae6e37f6f3895d674d89d40517f971615a1fadee091bfe02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1596c3344d6482fd910a604f15891f2ae30494de7f028a18c25ea139929a2890 0.600000000000 1558581 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": 1084350, "vin": [ { "gen": { "height": 1084340 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1596c3344d6482fd910a604f15891f2ae30494de7f028a18c25ea139929a2890" } } ], "extra": [ 1, 69, 174, 64, 25, 172, 217, 28, 115, 107, 174, 110, 55, 246, 243, 137, 93, 103, 77, 137, 212, 5, 23, 249, 113, 97, 90, 31, 173, 238, 9, 27, 254, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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