Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ead09dd0a4a36ad7b68ee9a24eb793c2c0f58b40a68ca20807072ded0fb2c306

Tx prefix hash: 6d156834420a48db739ee3a527cd8381d095bf79f784b2df57213fc797301bdc
Tx public key: a77c78f010886b211a5f3ef9c6f33f2a787e6f1bc6efdbed07daa8cf73e9dc34
Timestamp: 1734239813 Timestamp [UCT]: 2024-12-15 05:16:53 Age [y:d:h:m:s]: 00:329:03:56:54
Block: 1175517 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232749 RingCT/type: yes/0
Extra: 01a77c78f010886b211a5f3ef9c6f33f2a787e6f1bc6efdbed07daa8cf73e9dc34021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ed749e085eaf45c5a921c771ce5d4799fbed36829980c79e55866ce57e28f90 0.600000000000 1661808 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": 1175527, "vin": [ { "gen": { "height": 1175517 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ed749e085eaf45c5a921c771ce5d4799fbed36829980c79e55866ce57e28f90" } } ], "extra": [ 1, 167, 124, 120, 240, 16, 136, 107, 33, 26, 95, 62, 249, 198, 243, 63, 42, 120, 126, 111, 27, 198, 239, 219, 237, 7, 218, 168, 207, 115, 233, 220, 52, 2, 17, 0, 0, 0, 4, 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