Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74643d6e48786f989db3c518824d2c671b2e2bb1842a815fa58a019b640a2923

Tx prefix hash: f478c057646217753c4771e93b085def1d64c3a489475dc310f9405f61966525
Tx public key: 4118a7ae6df001bca612c18e9f535a9a3ba48ad284306be0e7fde87e707e41cd
Timestamp: 1725943482 Timestamp [UCT]: 2024-09-10 04:44:42 Age [y:d:h:m:s]: 00:278:13:48:35
Block: 1106836 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198874 RingCT/type: yes/0
Extra: 014118a7ae6df001bca612c18e9f535a9a3ba48ad284306be0e7fde87e707e41cd021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66a4b308ac844f17c8276f475560dd90bf0228f14a1372afc7296e55ee447dd5 0.600000000000 1584437 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": 1106846, "vin": [ { "gen": { "height": 1106836 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66a4b308ac844f17c8276f475560dd90bf0228f14a1372afc7296e55ee447dd5" } } ], "extra": [ 1, 65, 24, 167, 174, 109, 240, 1, 188, 166, 18, 193, 142, 159, 83, 90, 154, 59, 164, 138, 210, 132, 48, 107, 224, 231, 253, 232, 126, 112, 126, 65, 205, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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