Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48dc8d6e0a1068cf9708734a60f464be6dfa7c8a18c1e7fa798ec1782fb633d6

Tx prefix hash: 1c017b4817ca2d22831715f2aa6d9ef849fc4834667af465a52bf38c43103e9d
Tx public key: 4eac70fa00142fdd4baddaabccec46a7805762b2e12cf3b10ff8f44f8b1c06b3
Timestamp: 1723993813 Timestamp [UCT]: 2024-08-18 15:10:13 Age [y:d:h:m:s]: 00:101:17:15:48
Block: 1090673 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72752 RingCT/type: yes/0
Extra: 014eac70fa00142fdd4baddaabccec46a7805762b2e12cf3b10ff8f44f8b1c06b302110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 174f18c5b6e05805add9f8f2e15ac3559f1a63a64acf02c4398912cb56cbf96d 0.600000000000 1565296 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": 1090683, "vin": [ { "gen": { "height": 1090673 } } ], "vout": [ { "amount": 600000000, "target": { "key": "174f18c5b6e05805add9f8f2e15ac3559f1a63a64acf02c4398912cb56cbf96d" } } ], "extra": [ 1, 78, 172, 112, 250, 0, 20, 47, 221, 75, 173, 218, 171, 204, 236, 70, 167, 128, 87, 98, 178, 225, 44, 243, 177, 15, 248, 244, 79, 139, 28, 6, 179, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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