Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 057173c18d686a56e2014ba7ebe236514776d78410d6441668e25c8cfd5981d2

Tx prefix hash: d1d3533c3ce85ddce227e1d722798c7d4ecc6ce2e9510d0a3be902763b3bcbcd
Tx public key: c884c74d007c4a8dee97953d2e172212fa09e868a341c9d2b4c4bca56b4ff976
Timestamp: 1738307519 Timestamp [UCT]: 2025-01-31 07:11:59 Age [y:d:h:m:s]: 00:138:02:18:11
Block: 1208915 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98655 RingCT/type: yes/0
Extra: 01c884c74d007c4a8dee97953d2e172212fa09e868a341c9d2b4c4bca56b4ff976021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a0737c654773cf0014c1f562f1f17bba4277907a0417f7a654a7e0721ab8475 0.600000000000 1695652 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": 1208925, "vin": [ { "gen": { "height": 1208915 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a0737c654773cf0014c1f562f1f17bba4277907a0417f7a654a7e0721ab8475" } } ], "extra": [ 1, 200, 132, 199, 77, 0, 124, 74, 141, 238, 151, 149, 61, 46, 23, 34, 18, 250, 9, 232, 104, 163, 65, 201, 210, 180, 196, 188, 165, 107, 79, 249, 118, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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