Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f100d8d215b80dabd1ade53c383f91f1d63b8b4f792eda0d985d242f898a5fc

Tx prefix hash: cbf0ac6b728d4aeb31a44128a022934d3c3355694443a3dd1fff398c3dcc5bfb
Tx public key: 58b8bdeb1d8459b4c5b65580e1e88e1092302a793a948f6f8790090be01511ba
Timestamp: 1736174765 Timestamp [UCT]: 2025-01-06 14:46:05 Age [y:d:h:m:s]: 00:167:16:16:54
Block: 1191532 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119444 RingCT/type: yes/0
Extra: 0158b8bdeb1d8459b4c5b65580e1e88e1092302a793a948f6f8790090be01511ba0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f5df41fd8af1d2f76f3be27f3744293f147b2cd5d35d32f3652f40ae163808b 0.600000000000 1678071 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": 1191542, "vin": [ { "gen": { "height": 1191532 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f5df41fd8af1d2f76f3be27f3744293f147b2cd5d35d32f3652f40ae163808b" } } ], "extra": [ 1, 88, 184, 189, 235, 29, 132, 89, 180, 197, 182, 85, 128, 225, 232, 142, 16, 146, 48, 42, 121, 58, 148, 143, 111, 135, 144, 9, 11, 224, 21, 17, 186, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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