Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e472c9c0448123978b949fd7c6b12b99ccd5204f39087f87776bfc150f33205

Tx prefix hash: 554530cfda9b30cb0e8bafc2c7b38e0ff28bb5aa4ec1eb23fef231c71aebe3c5
Tx public key: 0a42f015938b3719f226dd14493b271b0b3246fdeea70979e460395931335ae3
Timestamp: 1745829364 Timestamp [UCT]: 2025-04-28 08:36:04 Age [y:d:h:m:s]: 00:009:19:36:34
Block: 1271181 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7013 RingCT/type: yes/0
Extra: 010a42f015938b3719f226dd14493b271b0b3246fdeea70979e460395931335ae302110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 681f22ea9be3e03854a1a5e4eaeb784c7c0220d9318e82b05e875d2501a197af 0.600000000000 1758436 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": 1271191, "vin": [ { "gen": { "height": 1271181 } } ], "vout": [ { "amount": 600000000, "target": { "key": "681f22ea9be3e03854a1a5e4eaeb784c7c0220d9318e82b05e875d2501a197af" } } ], "extra": [ 1, 10, 66, 240, 21, 147, 139, 55, 25, 242, 38, 221, 20, 73, 59, 39, 27, 11, 50, 70, 253, 238, 167, 9, 121, 228, 96, 57, 89, 49, 51, 90, 227, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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