Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f00e5d0651816de634edbb79af861977906cfc2d976065eb1cc9105e505ec9c

Tx prefix hash: 0d94c672cebcf54c4c2b7a95f6e2f3ca40e1c733616d4a71f43740e5b22a266b
Tx public key: 3fdf62ad0273c9714694bec4c4e372625874a8391696b175a76ad0e0d8ce99b6
Timestamp: 1696109571 Timestamp [UCT]: 2023-09-30 21:32:51 Age [y:d:h:m:s]: 01:114:10:06:00
Block: 859697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 343018 RingCT/type: yes/0
Extra: 013fdf62ad0273c9714694bec4c4e372625874a8391696b175a76ad0e0d8ce99b60211000000014b8f5122000000000000000000

1 output(s) for total of 0.869895340000 dcy

stealth address amount amount idx
00: 5e96a540c2abd5dda36499811999db8edfd64c233114cd2ada34afaebc624f9b 0.869895340000 1313937 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": 859707, "vin": [ { "gen": { "height": 859697 } } ], "vout": [ { "amount": 869895340, "target": { "key": "5e96a540c2abd5dda36499811999db8edfd64c233114cd2ada34afaebc624f9b" } } ], "extra": [ 1, 63, 223, 98, 173, 2, 115, 201, 113, 70, 148, 190, 196, 196, 227, 114, 98, 88, 116, 168, 57, 22, 150, 177, 117, 167, 106, 208, 224, 216, 206, 153, 182, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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