Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2461f9597f4605aa5b67eb24000defa2b2c178da710e626c2d3491a5fab577f9

Tx prefix hash: 218b2973a90c04b7b99749b2a5cd59c9327950f8f91fc0af960861f49d00006b
Tx public key: b6914c5ecf57f8d411d790560786c75a0ef5097bf099751a07a878eef10e80f2
Timestamp: 1696428577 Timestamp [UCT]: 2023-10-04 14:09:37 Age [y:d:h:m:s]: 01:148:20:00:39
Block: 862336 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367391 RingCT/type: yes/0
Extra: 01b6914c5ecf57f8d411d790560786c75a0ef5097bf099751a07a878eef10e80f202110000000775e3f0e9000000000000000000

1 output(s) for total of 0.852555966000 dcy

stealth address amount amount idx
00: 993aaf1e26b4a3eec3b8e8b87a69f92a11bb980af28a2be01868e00219bde971 0.852555966000 1316754 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": 862346, "vin": [ { "gen": { "height": 862336 } } ], "vout": [ { "amount": 852555966, "target": { "key": "993aaf1e26b4a3eec3b8e8b87a69f92a11bb980af28a2be01868e00219bde971" } } ], "extra": [ 1, 182, 145, 76, 94, 207, 87, 248, 212, 17, 215, 144, 86, 7, 134, 199, 90, 14, 245, 9, 123, 240, 153, 117, 26, 7, 168, 120, 238, 241, 14, 128, 242, 2, 17, 0, 0, 0, 7, 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