Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04eceb83223fb3c2353cfb61179986c82583f16791883b0607b0509e723d4c7d

Tx prefix hash: 4adc994c47c190bd96c307c1618c79c98469e974921249b90923c9d975cdcd76
Tx public key: bef8b93fb6d630f599bede0e560b99b10d8df051545c9078529e434e78ebd01b
Timestamp: 1704016571 Timestamp [UCT]: 2023-12-31 09:56:11 Age [y:d:h:m:s]: 01:092:00:39:35
Block: 925034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326877 RingCT/type: yes/0
Extra: 01bef8b93fb6d630f599bede0e560b99b10d8df051545c9078529e434e78ebd01b0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7b62ba4f755e4862f4e05d7f8725efc4f19f6ceeff74fcbea970a01417d252a 0.600000000000 1382794 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": 925044, "vin": [ { "gen": { "height": 925034 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7b62ba4f755e4862f4e05d7f8725efc4f19f6ceeff74fcbea970a01417d252a" } } ], "extra": [ 1, 190, 248, 185, 63, 182, 214, 48, 245, 153, 190, 222, 14, 86, 11, 153, 177, 13, 141, 240, 81, 84, 92, 144, 120, 82, 158, 67, 78, 120, 235, 208, 27, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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