Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cd344223b34a77bc187f3b5fa4ae3b9ac4ce6ce64e56e95950f3901157790eb

Tx prefix hash: 22252be9671e1bc0a724c3726770f51738559dbfdbc3b2146797d8b603794c73
Tx public key: ad29cb5cd46ed83cf6ec1f9f7cd841c9f7a6e84dd50c45860e11ac944575916c
Timestamp: 1733456231 Timestamp [UCT]: 2024-12-06 03:37:11 Age [y:d:h:m:s]: 00:158:03:27:19
Block: 1169008 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112847 RingCT/type: yes/0
Extra: 01ad29cb5cd46ed83cf6ec1f9f7cd841c9f7a6e84dd50c45860e11ac944575916c0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4073d85b405c1d6ac7d74d2d8edb1defdb4997e66ffa6e4795d6a1175c6ec230 0.600000000000 1654721 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": 1169018, "vin": [ { "gen": { "height": 1169008 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4073d85b405c1d6ac7d74d2d8edb1defdb4997e66ffa6e4795d6a1175c6ec230" } } ], "extra": [ 1, 173, 41, 203, 92, 212, 110, 216, 60, 246, 236, 31, 159, 124, 216, 65, 201, 247, 166, 232, 77, 213, 12, 69, 134, 14, 17, 172, 148, 69, 117, 145, 108, 2, 17, 0, 0, 0, 2, 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