Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 530b72273512d4150cc142bbd9334de273d56f8140ca78b9742aa0eed19b5701

Tx prefix hash: 2d1dc646de807ef1c24fc11f3b7fd2dd5dc978c5e1ff1a1d8eb4873b8abd7e84
Tx public key: 124e0d26e1fb06439c11452f2d1135bd484c9a1a28f292e80599228600977034
Timestamp: 1756220958 Timestamp [UCT]: 2025-08-26 15:09:18 Age [y:d:h:m:s]: 00:093:08:18:48
Block: 1354920 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66668 RingCT/type: yes/0
Extra: 01124e0d26e1fb06439c11452f2d1135bd484c9a1a28f292e805992286009770340211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51a46d746ba7fe06aaf6618bbf3ca72fd4ee8b712dc8a5e9ebc3ebc4a74b8c41 0.600000000000 1842915 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": 1354930, "vin": [ { "gen": { "height": 1354920 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51a46d746ba7fe06aaf6618bbf3ca72fd4ee8b712dc8a5e9ebc3ebc4a74b8c41" } } ], "extra": [ 1, 18, 78, 13, 38, 225, 251, 6, 67, 156, 17, 69, 47, 45, 17, 53, 189, 72, 76, 154, 26, 40, 242, 146, 232, 5, 153, 34, 134, 0, 151, 112, 52, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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