Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a1b763956db83acc3233bb73a654e0d4a3a0c3e2affdcfcf72bc1fc2e24ce71

Tx prefix hash: 7e4f6ab3d2141999654dfb1875adc74784cba6a1f0367a9fcc99da6e1529b1bc
Tx public key: e5dcd42f7b72338cd89e129661e025c385670bfbc90290beca3d7da9a28898f5
Timestamp: 1736057797 Timestamp [UCT]: 2025-01-05 06:16:37 Age [y:d:h:m:s]: 00:167:17:02:14
Block: 1190559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119496 RingCT/type: yes/0
Extra: 01e5dcd42f7b72338cd89e129661e025c385670bfbc90290beca3d7da9a28898f502110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb56e362ac001a94c5ebae8b6b6bbff1d205665bdf7b4e2a9a88a8c1b70e9b65 0.600000000000 1677076 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": 1190569, "vin": [ { "gen": { "height": 1190559 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb56e362ac001a94c5ebae8b6b6bbff1d205665bdf7b4e2a9a88a8c1b70e9b65" } } ], "extra": [ 1, 229, 220, 212, 47, 123, 114, 51, 140, 216, 158, 18, 150, 97, 224, 37, 195, 133, 103, 11, 251, 201, 2, 144, 190, 202, 61, 125, 169, 162, 136, 152, 245, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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