Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea8b421e04e8ff180d21e8cea81d8e559d50954356b9f27fb9dc3a0a64c22546

Tx prefix hash: 5bc810450038d4ed874eed8cc7a87dad433c5da4e1f1d3a6cc126887746d7deb
Tx public key: 7b7793e40d883262d2c66381a7f220d3fc23e84b5ebd860158d4975a32468a22
Timestamp: 1732530045 Timestamp [UCT]: 2024-11-25 10:20:45 Age [y:d:h:m:s]: 00:359:03:47:48
Block: 1161336 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254234 RingCT/type: yes/0
Extra: 017b7793e40d883262d2c66381a7f220d3fc23e84b5ebd860158d4975a32468a220211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f3ee244d6a283449c93f7a72656a9179e29835b4f442ec1815bd86fd4250c3f 0.600000000000 1646987 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": 1161346, "vin": [ { "gen": { "height": 1161336 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f3ee244d6a283449c93f7a72656a9179e29835b4f442ec1815bd86fd4250c3f" } } ], "extra": [ 1, 123, 119, 147, 228, 13, 136, 50, 98, 210, 198, 99, 129, 167, 242, 32, 211, 252, 35, 232, 75, 94, 189, 134, 1, 88, 212, 151, 90, 50, 70, 138, 34, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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