Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: feddce9f44a489e776e2ec566ee120cff30d756b594df14aa6e4a7d2ed66af44

Tx prefix hash: b732deb947e14dee441041b4ea22c159bfd6fd9afed8b9f342fc37634b6c565f
Tx public key: 4f3c0ebdf56e5fff2235b724917329adb44dc78a36fbd19c4a738ab45d820794
Timestamp: 1731455866 Timestamp [UCT]: 2024-11-12 23:57:46 Age [y:d:h:m:s]: 00:143:19:18:53
Block: 1152428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102608 RingCT/type: yes/0
Extra: 014f3c0ebdf56e5fff2235b724917329adb44dc78a36fbd19c4a738ab45d8207940211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 661ea7521a2df6f2b0c2d5ddf1f9e0c976539ca4932f49635d3488501f4925ad 0.600000000000 1638025 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": 1152438, "vin": [ { "gen": { "height": 1152428 } } ], "vout": [ { "amount": 600000000, "target": { "key": "661ea7521a2df6f2b0c2d5ddf1f9e0c976539ca4932f49635d3488501f4925ad" } } ], "extra": [ 1, 79, 60, 14, 189, 245, 110, 95, 255, 34, 53, 183, 36, 145, 115, 41, 173, 180, 77, 199, 138, 54, 251, 209, 156, 74, 115, 138, 180, 93, 130, 7, 148, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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