Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: feae155561dbdc08bc6e8b4fab9453217f0666ca0d668456e081b7d0ad4baa05

Tx prefix hash: 36ae5792ff2a4424c3928d7e8f2300ba8c1f3f4e4ab7f1e01bab7ced992fa269
Tx public key: 948a8186ec8d6c9423066120c701b0b328ac842d7aa2d3fbc408538d39baee5b
Timestamp: 1702801570 Timestamp [UCT]: 2023-12-17 08:26:10 Age [y:d:h:m:s]: 01:185:12:01:40
Block: 914974 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393610 RingCT/type: yes/0
Extra: 01948a8186ec8d6c9423066120c701b0b328ac842d7aa2d3fbc408538d39baee5b02110000000875e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 47938369cf6c41c78075fc66e7209d5fee92f29f0ff15e8b154fedd4174b2476 0.600000000000 1372340 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": 914984, "vin": [ { "gen": { "height": 914974 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47938369cf6c41c78075fc66e7209d5fee92f29f0ff15e8b154fedd4174b2476" } } ], "extra": [ 1, 148, 138, 129, 134, 236, 141, 108, 148, 35, 6, 97, 32, 199, 1, 176, 179, 40, 172, 132, 45, 122, 162, 211, 251, 196, 8, 83, 141, 57, 186, 238, 91, 2, 17, 0, 0, 0, 8, 117, 227, 240, 233, 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