Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcfe9c758aeccbc445ae0f142853340ed0d9ba81fbb3ff8022b4395195b809a6

Tx prefix hash: 0c90cbe110923332482076e0ffd14025f0a3b809409d612357abafed344a9739
Tx public key: 715ae5e1064355df44e1c985d154c5d6a7b4cd8fcff4f27356f1607b33c6b2c5
Timestamp: 1720728752 Timestamp [UCT]: 2024-07-11 20:12:32 Age [y:d:h:m:s]: 00:314:22:59:41
Block: 1063606 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225070 RingCT/type: yes/0
Extra: 01715ae5e1064355df44e1c985d154c5d6a7b4cd8fcff4f27356f1607b33c6b2c502110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e74c60bf9ab1efd82d904b84ac5bed8882da21f52d78869bae5db71762e7155e 0.600000000000 1534123 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": 1063616, "vin": [ { "gen": { "height": 1063606 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e74c60bf9ab1efd82d904b84ac5bed8882da21f52d78869bae5db71762e7155e" } } ], "extra": [ 1, 113, 90, 229, 225, 6, 67, 85, 223, 68, 225, 201, 133, 209, 84, 197, 214, 167, 180, 205, 143, 207, 244, 242, 115, 86, 241, 96, 123, 51, 198, 178, 197, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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