Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88da3e1864b6b900d31ffdce72f74c5410f41a2e9b8df390188db1b630bb613b

Tx prefix hash: 90d922ce82acdb0a4e25665649634f4da27a65e6547ba9e607f5bce355324dfb
Tx public key: 28cbe2857c5ea18009bee9b9c133553724281f939b192cd4e6e18d559e57a6a5
Timestamp: 1724660347 Timestamp [UCT]: 2024-08-26 08:19:07 Age [y:d:h:m:s]: 00:223:17:26:59
Block: 1096186 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159750 RingCT/type: yes/0
Extra: 0128cbe2857c5ea18009bee9b9c133553724281f939b192cd4e6e18d559e57a6a502110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa616ea7fa3f6ff1301aac43ca6272ce1a41d77966a611a57bcb94f17414bc3b 0.600000000000 1571373 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": 1096196, "vin": [ { "gen": { "height": 1096186 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa616ea7fa3f6ff1301aac43ca6272ce1a41d77966a611a57bcb94f17414bc3b" } } ], "extra": [ 1, 40, 203, 226, 133, 124, 94, 161, 128, 9, 190, 233, 185, 193, 51, 85, 55, 36, 40, 31, 147, 155, 25, 44, 212, 230, 225, 141, 85, 158, 87, 166, 165, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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