Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5da8a74719cf1e1afc4a644a3fb6191f8afb8cbe2ad8d222374a6980c7b853c4

Tx prefix hash: eb1cfa91785ee4ef4a1b9b623dbe39e3cfcb9441112504be60f0bce8f659d2f3
Tx public key: c1748cb651440055e0d0f612474505c5f6a8c559f67fc719cba790c43d4930b0
Timestamp: 1580784379 Timestamp [UCT]: 2020-02-04 02:46:19 Age [y:d:h:m:s]: 05:002:00:01:30
Block: 58033 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1153596 RingCT/type: yes/0
Extra: 01c1748cb651440055e0d0f612474505c5f6a8c559f67fc719cba790c43d4930b002110000000249b77a3d000000000000000000

1 output(s) for total of 394.197078759000 dcy

stealth address amount amount idx
00: d2ad990e2b6302e71c55cb9cd9c5f0efc794df7b807f530d555b26335243bcbe 394.197078759000 107320 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": 58043, "vin": [ { "gen": { "height": 58033 } } ], "vout": [ { "amount": 394197078759, "target": { "key": "d2ad990e2b6302e71c55cb9cd9c5f0efc794df7b807f530d555b26335243bcbe" } } ], "extra": [ 1, 193, 116, 140, 182, 81, 68, 0, 85, 224, 208, 246, 18, 71, 69, 5, 197, 246, 168, 197, 89, 246, 127, 199, 25, 203, 167, 144, 196, 61, 73, 48, 176, 2, 17, 0, 0, 0, 2, 73, 183, 122, 61, 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