Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1030a691777b43ef07c1fa1d77640206a47c0d8fa8a2f00cde573a5e71f7f58

Tx prefix hash: a554461e43c59a86f6978db14276c0cf1b79f67e1e41b54917bb9a65cd9d5925
Tx public key: 7125005a2dd24f0dd08fe118757a3520f6b6a7f0b427a48226828edf6b0ad827
Timestamp: 1734089746 Timestamp [UCT]: 2024-12-13 11:35:46 Age [y:d:h:m:s]: 00:108:18:37:00
Block: 1174276 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77510 RingCT/type: yes/0
Extra: 017125005a2dd24f0dd08fe118757a3520f6b6a7f0b427a48226828edf6b0ad827021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38717c4f4c0e1d369ebf74fbafdd1cc02b1f36dc8186f3bc687193ded66137aa 0.600000000000 1660409 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": 1174286, "vin": [ { "gen": { "height": 1174276 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38717c4f4c0e1d369ebf74fbafdd1cc02b1f36dc8186f3bc687193ded66137aa" } } ], "extra": [ 1, 113, 37, 0, 90, 45, 210, 79, 13, 208, 143, 225, 24, 117, 122, 53, 32, 246, 182, 167, 240, 180, 39, 164, 130, 38, 130, 142, 223, 107, 10, 216, 39, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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