Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2cb8824218b88242352766af04c485c16b0dc940d7ffb07d512df35457d32ca

Tx prefix hash: 08d80c5542a34a07ee45c5bca78dd000ae88da0a4d48cd0f80802f74c47d5aa4
Tx public key: 122d29782e768f857dffcecc811cb0c922aeedd9bf5cd3da0e084026d1d9300a
Timestamp: 1735372986 Timestamp [UCT]: 2024-12-28 08:03:06 Age [y:d:h:m:s]: 00:081:15:24:04
Block: 1184879 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58155 RingCT/type: yes/0
Extra: 01122d29782e768f857dffcecc811cb0c922aeedd9bf5cd3da0e084026d1d9300a0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f94c3b7d738f2bf99f86ed5559403f817da89f5eccbdcb02d60bb25eed1bb018 0.600000000000 1671338 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": 1184889, "vin": [ { "gen": { "height": 1184879 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f94c3b7d738f2bf99f86ed5559403f817da89f5eccbdcb02d60bb25eed1bb018" } } ], "extra": [ 1, 18, 45, 41, 120, 46, 118, 143, 133, 125, 255, 206, 204, 129, 28, 176, 201, 34, 174, 237, 217, 191, 92, 211, 218, 14, 8, 64, 38, 209, 217, 48, 10, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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