Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01486491bd8053cb27d8cf9d1e082402a74d7c3840984ff4da7f70ab4a61b0b8

Tx prefix hash: 61a037b661a23f83f7676f6ff1f3b1338f1754a23863a4ad058bbef1df8a15d9
Tx public key: 794ae0bf70f11c39a4abfd573af8dd374dba43360d65774a245cc6ab6ad27853
Timestamp: 1695557308 Timestamp [UCT]: 2023-09-24 12:08:28 Age [y:d:h:m:s]: 01:197:10:30:55
Block: 855108 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 402171 RingCT/type: yes/0
Extra: 01794ae0bf70f11c39a4abfd573af8dd374dba43360d65774a245cc6ab6ad27853021100000003faf35c9c000000000000000000

1 output(s) for total of 0.900891051000 dcy

stealth address amount amount idx
00: 0291a9b0e4763c8a7014ea19139f9640b8b7bfdbf3e402091cafe9b56e3ebb30 0.900891051000 1309112 of 0

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": 855118, "vin": [ { "gen": { "height": 855108 } } ], "vout": [ { "amount": 900891051, "target": { "key": "0291a9b0e4763c8a7014ea19139f9640b8b7bfdbf3e402091cafe9b56e3ebb30" } } ], "extra": [ 1, 121, 74, 224, 191, 112, 241, 28, 57, 164, 171, 253, 87, 58, 248, 221, 55, 77, 186, 67, 54, 13, 101, 119, 74, 36, 92, 198, 171, 106, 210, 120, 83, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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