Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 675cd96ab23077e5dd0ab3d8a5fb8279d4cf25d5b000e664eac4f58174143f91

Tx prefix hash: fb3cef01dfd6e2f3591e57bf4bdd37f92f8e9ddd7237656d5a3fe7f8a7343f85
Tx public key: 1a2f7ce178badc56deab94381474a45a702e8c2cad59f65165fd68c915b8dab6
Timestamp: 1699868575 Timestamp [UCT]: 2023-11-13 09:42:55 Age [y:d:h:m:s]: 02:010:06:30:53
Block: 890664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 527109 RingCT/type: yes/0
Extra: 011a2f7ce178badc56deab94381474a45a702e8c2cad59f65165fd68c915b8dab602110000000633af99f4000000000000000000

1 output(s) for total of 0.686847676000 dcy

stealth address amount amount idx
00: f7384fefdb484700d8689aa18517bdb55dd39a9f91d465878dd58d3fb07ece5a 0.686847676000 1346693 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": 890674, "vin": [ { "gen": { "height": 890664 } } ], "vout": [ { "amount": 686847676, "target": { "key": "f7384fefdb484700d8689aa18517bdb55dd39a9f91d465878dd58d3fb07ece5a" } } ], "extra": [ 1, 26, 47, 124, 225, 120, 186, 220, 86, 222, 171, 148, 56, 20, 116, 164, 90, 112, 46, 140, 44, 173, 89, 246, 81, 101, 253, 104, 201, 21, 184, 218, 182, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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