Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4bb1d6e9153e316f2141df34e7c65a311a5690e5e9535460851ae0e675fff98

Tx prefix hash: 82142cc31ee0c64b43777899ea87c27757fd78a1bd02ce2d9e1295d504c297df
Tx public key: ab6d993292740d639e36c7a68a5e326cd609101f00d422f3f19558546aa7d2fe
Timestamp: 1702326345 Timestamp [UCT]: 2023-12-11 20:25:45 Age [y:d:h:m:s]: 02:010:22:03:18
Block: 911041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 527574 RingCT/type: yes/0
Extra: 01ab6d993292740d639e36c7a68a5e326cd609101f00d422f3f19558546aa7d2fe02110000000ce6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d047d7aed3e112a21cbe8418088c852dfaf4fc2e6e38452087378169d973257b 0.600000000000 1368216 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": 911051, "vin": [ { "gen": { "height": 911041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d047d7aed3e112a21cbe8418088c852dfaf4fc2e6e38452087378169d973257b" } } ], "extra": [ 1, 171, 109, 153, 50, 146, 116, 13, 99, 158, 54, 199, 166, 138, 94, 50, 108, 214, 9, 16, 31, 0, 212, 34, 243, 241, 149, 88, 84, 106, 167, 210, 254, 2, 17, 0, 0, 0, 12, 230, 210, 127, 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