Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74d1c2334fd4f13c459908567738e89a62e86bc612dfda2822181b58ec3081c4

Tx prefix hash: f887d7a0a83d570c484ed6b3ae5844d1cca080e07d9c31b358787d4e8a7b8b30
Tx public key: 1ad2e0180130645b67c2b4d9af0c2c19d7d4f99ef8f3c7e8e76da9333e5e0ebb
Timestamp: 1730340821 Timestamp [UCT]: 2024-10-31 02:13:41 Age [y:d:h:m:s]: 00:082:11:39:18
Block: 1143201 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58972 RingCT/type: yes/0
Extra: 011ad2e0180130645b67c2b4d9af0c2c19d7d4f99ef8f3c7e8e76da9333e5e0ebb02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7caf31dd3fe57a293d07031ca5edd1251dd0f8784fa83d1c3e0d330f643a544 0.600000000000 1627064 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": 1143211, "vin": [ { "gen": { "height": 1143201 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7caf31dd3fe57a293d07031ca5edd1251dd0f8784fa83d1c3e0d330f643a544" } } ], "extra": [ 1, 26, 210, 224, 24, 1, 48, 100, 91, 103, 194, 180, 217, 175, 12, 44, 25, 215, 212, 249, 158, 248, 243, 199, 232, 231, 109, 169, 51, 62, 94, 14, 187, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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