Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc5d0058a5df8f024674b1416a3968d047217d6436ace66cd0d3401d5cb474b4

Tx prefix hash: af3de38dc1dc6b4a12d6028ca762575f9468a94de11ae5fb60ad3ec6467a65d3
Tx public key: 1169201f443359e622bf19ce8d527e3e63217fe0f82273fd27cfea4e59f4f539
Timestamp: 1737843569 Timestamp [UCT]: 2025-01-25 22:19:29 Age [y:d:h:m:s]: 00:048:02:25:58
Block: 1205291 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34195 RingCT/type: yes/0
Extra: 011169201f443359e622bf19ce8d527e3e63217fe0f82273fd27cfea4e59f4f539021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48c8e9a89e0e277853a0b606d75542f10ce50bbb7b2ff9aaf8df149b5caa9d82 0.600000000000 1691988 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": 1205301, "vin": [ { "gen": { "height": 1205291 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48c8e9a89e0e277853a0b606d75542f10ce50bbb7b2ff9aaf8df149b5caa9d82" } } ], "extra": [ 1, 17, 105, 32, 31, 68, 51, 89, 230, 34, 191, 25, 206, 141, 82, 126, 62, 99, 33, 127, 224, 248, 34, 115, 253, 39, 207, 234, 78, 89, 244, 245, 57, 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