Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e0bf478fdd8400a14d9d585865a58818a8e5b9799ed6c6a18974eaeebf3b92b

Tx prefix hash: cc8cae5a3a4bd0587a33aa40dd8788b345a6f36456ac0026905c7ee097088d4d
Tx public key: fe89a3de5cfcd5a6f66ac3f6fac0cbbd1f76c3a6aa41852f5be09028c55fb2d1
Timestamp: 1699569018 Timestamp [UCT]: 2023-11-09 22:30:18 Age [y:d:h:m:s]: 01:147:17:48:40
Block: 888176 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366777 RingCT/type: yes/0
Extra: 01fe89a3de5cfcd5a6f66ac3f6fac0cbbd1f76c3a6aa41852f5be09028c55fb2d102110000000333af99f4000000000000000000

1 output(s) for total of 0.700009950000 dcy

stealth address amount amount idx
00: 865fae63dd424e392b5e1f805591941bc20d64eab33e8d7cb5aa7c314deeafc4 0.700009950000 1344107 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": 888186, "vin": [ { "gen": { "height": 888176 } } ], "vout": [ { "amount": 700009950, "target": { "key": "865fae63dd424e392b5e1f805591941bc20d64eab33e8d7cb5aa7c314deeafc4" } } ], "extra": [ 1, 254, 137, 163, 222, 92, 252, 213, 166, 246, 106, 195, 246, 250, 192, 203, 189, 31, 118, 195, 166, 170, 65, 133, 47, 91, 224, 144, 40, 197, 95, 178, 209, 2, 17, 0, 0, 0, 3, 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