Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e96dd7142b437fb4c468b540866b60583872e922edebfc27bdb2d1b25038c665

Tx prefix hash: 654fcf79436e71c529a697092ae2c2f95a8abcdecd7c19a3b7f4808bef9fa8fc
Tx public key: c6f2044dcd49ae30ce0badf373769a3c6ed476dca9da1f18711d74ff46053aa6
Timestamp: 1698260289 Timestamp [UCT]: 2023-10-25 18:58:09 Age [y:d:h:m:s]: 01:161:07:01:05
Block: 877534 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 376268 RingCT/type: yes/0
Extra: 01c6f2044dcd49ae30ce0badf373769a3c6ed476dca9da1f18711d74ff46053aa602110000000475e3f0e9000000000000000000

1 output(s) for total of 0.759216421000 dcy

stealth address amount amount idx
00: 12bb7add3c84165b836ff78c323f630b8857907f2ad250689d7f4bc66cf96380 0.759216421000 1332916 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": 877544, "vin": [ { "gen": { "height": 877534 } } ], "vout": [ { "amount": 759216421, "target": { "key": "12bb7add3c84165b836ff78c323f630b8857907f2ad250689d7f4bc66cf96380" } } ], "extra": [ 1, 198, 242, 4, 77, 205, 73, 174, 48, 206, 11, 173, 243, 115, 118, 154, 60, 110, 212, 118, 220, 169, 218, 31, 24, 113, 29, 116, 255, 70, 5, 58, 166, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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