Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb165ac58a114663edd0c77f5f8a556e553044f4eebc405051d149a059e22979

Tx prefix hash: a7b2b0e4ec2d0fca4547339e5a6f92af05ddf6b9bc2a79dfadc7bef6052bc850
Tx public key: 5fa46a8007964f4fa82d155b2f57f70ec02515c3874d6dd23a3b71cf48878bfb
Timestamp: 1580567559 Timestamp [UCT]: 2020-02-01 14:32:39 Age [y:d:h:m:s]: 04:289:14:00:06
Block: 56516 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1098217 RingCT/type: yes/0
Extra: 015fa46a8007964f4fa82d155b2f57f70ec02515c3874d6dd23a3b71cf48878bfb02110000000117786bcf000000000000000000

1 output(s) for total of 398.792855191000 dcy

stealth address amount amount idx
00: da656277b180942ae256a5aa64b1e5fba995c40561dc15a659f7e8dbc1e64460 398.792855191000 104247 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": 56526, "vin": [ { "gen": { "height": 56516 } } ], "vout": [ { "amount": 398792855191, "target": { "key": "da656277b180942ae256a5aa64b1e5fba995c40561dc15a659f7e8dbc1e64460" } } ], "extra": [ 1, 95, 164, 106, 128, 7, 150, 79, 79, 168, 45, 21, 91, 47, 87, 247, 14, 192, 37, 21, 195, 135, 77, 109, 210, 58, 59, 113, 207, 72, 135, 139, 251, 2, 17, 0, 0, 0, 1, 23, 120, 107, 207, 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