Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45292d0fdb80d40ab3d4237a05f0120206cb4ee207070e85d15722bf86393b93

Tx prefix hash: d37f1bc526702d8cb4b883b817c5d5a7e17985c8003a651970523178c673eb72
Tx public key: 797b332ef978f8e5950afb0e0dc5fa7dfc2094cc90b5ae2ccfec95f59e1bb0b5
Timestamp: 1735306732 Timestamp [UCT]: 2024-12-27 13:38:52 Age [y:d:h:m:s]: 00:123:00:12:10
Block: 1184325 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87736 RingCT/type: yes/0
Extra: 01797b332ef978f8e5950afb0e0dc5fa7dfc2094cc90b5ae2ccfec95f59e1bb0b5021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4bc6e2b4db45095d5024c2ce952ae8b372513e0b67889e59078d31d3583ca479 0.600000000000 1670782 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": 1184335, "vin": [ { "gen": { "height": 1184325 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4bc6e2b4db45095d5024c2ce952ae8b372513e0b67889e59078d31d3583ca479" } } ], "extra": [ 1, 121, 123, 51, 46, 249, 120, 248, 229, 149, 10, 251, 14, 13, 197, 250, 125, 252, 32, 148, 204, 144, 181, 174, 44, 207, 236, 149, 245, 158, 27, 176, 181, 2, 17, 0, 0, 0, 3, 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