Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b08ca9cfdf8fae5fbc3ce46903e4183e049d2238aab1d319539b5089fc858c2f

Tx prefix hash: b03752dcf9e546d24455819880f0054f0197c2db72f14b6de660ee67e627dc7c
Tx public key: cc29a56317088b810a1447d6d321e206c5c4924e3bd87836211406213e3f91d4
Timestamp: 1717626451 Timestamp [UCT]: 2024-06-05 22:27:31 Age [y:d:h:m:s]: 00:178:13:58:35
Block: 1037875 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127827 RingCT/type: yes/0
Extra: 01cc29a56317088b810a1447d6d321e206c5c4924e3bd87836211406213e3f91d402110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e82d4dc9914d6e2b26ff0ab42c32fd35d3d5507e4debb14a1e5ad00b36a9beee 0.600000000000 1506432 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": 1037885, "vin": [ { "gen": { "height": 1037875 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e82d4dc9914d6e2b26ff0ab42c32fd35d3d5507e4debb14a1e5ad00b36a9beee" } } ], "extra": [ 1, 204, 41, 165, 99, 23, 8, 139, 129, 10, 20, 71, 214, 211, 33, 226, 6, 197, 196, 146, 78, 59, 216, 120, 54, 33, 20, 6, 33, 62, 63, 145, 212, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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