Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cf2a1ee0f0bd5bfe48f6214d68ff24713c380eae4ffd33933c5e764dc4491db

Tx prefix hash: b42185312086bc856eef2ac386648ddd6bc820439ba071499c7c4d9d1eaa2d2f
Tx public key: e979bc2b7753f85886c6198f8ddb5fd66b3922fe2d1a3c7baf3ccf59d7a1dd09
Timestamp: 1701741216 Timestamp [UCT]: 2023-12-05 01:53:36 Age [y:d:h:m:s]: 01:105:09:24:22
Block: 906173 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336493 RingCT/type: yes/0
Extra: 01e979bc2b7753f85886c6198f8ddb5fd66b3922fe2d1a3c7baf3ccf59d7a1dd090211000000024b8f5122000000000000000000

1 output(s) for total of 0.610200635000 dcy

stealth address amount amount idx
00: 4c88ba4ff6ec38a99ce723bdb0120bcd70f42df54cde958cc8c8d81d1d460407 0.610200635000 1363100 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": 906183, "vin": [ { "gen": { "height": 906173 } } ], "vout": [ { "amount": 610200635, "target": { "key": "4c88ba4ff6ec38a99ce723bdb0120bcd70f42df54cde958cc8c8d81d1d460407" } } ], "extra": [ 1, 233, 121, 188, 43, 119, 83, 248, 88, 134, 198, 25, 143, 141, 219, 95, 214, 107, 57, 34, 254, 45, 26, 60, 123, 175, 60, 207, 89, 215, 161, 221, 9, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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