Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 479e68effee6aac3965d38b6411db57d06326114a5ad7ce3a7740f959188c2f4

Tx prefix hash: 657ed28756adc2a394d3ad3f95d4e2a5eacd114567a99c93b270b7f984294fcf
Tx public key: a2feaa345e4d8c0013a6a4b2f5989273d04469f3b01567237303262e64a66b66
Timestamp: 1753166969 Timestamp [UCT]: 2025-07-22 06:49:29 Age [y:d:h:m:s]: 00:075:16:40:33
Block: 1330775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 52842 RingCT/type: yes/0
Extra: 01a2feaa345e4d8c0013a6a4b2f5989273d04469f3b01567237303262e64a66b66021100000001bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 038b0f5060643e75d2905b070947d08598eef55884b08015fedc0af6e57315cb 0.600000000000 1818568 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": 1330785, "vin": [ { "gen": { "height": 1330775 } } ], "vout": [ { "amount": 600000000, "target": { "key": "038b0f5060643e75d2905b070947d08598eef55884b08015fedc0af6e57315cb" } } ], "extra": [ 1, 162, 254, 170, 52, 94, 77, 140, 0, 19, 166, 164, 178, 245, 152, 146, 115, 208, 68, 105, 243, 176, 21, 103, 35, 115, 3, 38, 46, 100, 166, 107, 102, 2, 17, 0, 0, 0, 1, 191, 81, 178, 162, 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