Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89456ad0a038d7ea3ebc97b322b66ae728de1b04348b1ed7a9de6c1c56f5365f

Tx prefix hash: 8bec7f6136dc2e498fedd86669e5f032921d6871089350e9b3f0b53c7b021ddf
Tx public key: 2f4bc32a267c281ccd45449c09f1337aedd8c20bfc7b3c39dd211ea250ef140b
Timestamp: 1741385454 Timestamp [UCT]: 2025-03-07 22:10:54 Age [y:d:h:m:s]: 00:258:11:26:02
Block: 1234386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182472 RingCT/type: yes/0
Extra: 012f4bc32a267c281ccd45449c09f1337aedd8c20bfc7b3c39dd211ea250ef140b021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7772b055a938a5ea44b42c55a51956c2ff94097359721c9c2c6f4ca96827c5d 0.600000000000 1721313 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": 1234396, "vin": [ { "gen": { "height": 1234386 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7772b055a938a5ea44b42c55a51956c2ff94097359721c9c2c6f4ca96827c5d" } } ], "extra": [ 1, 47, 75, 195, 42, 38, 124, 40, 28, 205, 69, 68, 156, 9, 241, 51, 122, 237, 216, 194, 11, 252, 123, 60, 57, 221, 33, 30, 162, 80, 239, 20, 11, 2, 17, 0, 0, 0, 2, 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