Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d1d208abaa8e17f7e76e8cd75685e383c5ded22169fbbfced02b3d9b2cb3beb

Tx prefix hash: ec9f3d213ea911ef4047b9081f2f83ec148da884e47a7551e8d1d8b9160f33ec
Tx public key: 85bdf73177bc585fbfdac8e107ab29cc49afd7c60fb9f7797a9b44856a2cf19c
Timestamp: 1721418497 Timestamp [UCT]: 2024-07-19 19:48:17 Age [y:d:h:m:s]: 00:247:09:42:01
Block: 1069338 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176702 RingCT/type: yes/0
Extra: 0185bdf73177bc585fbfdac8e107ab29cc49afd7c60fb9f7797a9b44856a2cf19c0211000000018fda9b2d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b580fc32b2697162850ef4f679f47ed31520748d4bab1ac5ef54e0d836ab6a3d 0.600000000000 1540719 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": 1069348, "vin": [ { "gen": { "height": 1069338 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b580fc32b2697162850ef4f679f47ed31520748d4bab1ac5ef54e0d836ab6a3d" } } ], "extra": [ 1, 133, 189, 247, 49, 119, 188, 88, 95, 191, 218, 200, 225, 7, 171, 41, 204, 73, 175, 215, 198, 15, 185, 247, 121, 122, 155, 68, 133, 106, 44, 241, 156, 2, 17, 0, 0, 0, 1, 143, 218, 155, 45, 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