Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1da28dcd459079c02b6ce01656a2c5493885d60d5739865d86ca426620e293f2

Tx prefix hash: 4f2fb3f9e2787778648e0535cdac071d9aa7ef6f9ab87eac9030522569381619
Tx public key: 436f0ad394f8ba85ba1b5d1a18ea3c6ba45de7444bd294e2e70575340a8416dd
Timestamp: 1685451565 Timestamp [UCT]: 2023-05-30 12:59:25 Age [y:d:h:m:s]: 02:023:13:59:52
Block: 771379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 538782 RingCT/type: yes/0
Extra: 01436f0ad394f8ba85ba1b5d1a18ea3c6ba45de7444bd294e2e70575340a8416dd021100000003e6d27f9c000000000000000000

1 output(s) for total of 1.706480501000 dcy

stealth address amount amount idx
00: c9d7a126d4bf1aecd02232b9aef3bed6103ab03e9d804b107c41859057bb14b1 1.706480501000 1220742 of 0

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": 771389, "vin": [ { "gen": { "height": 771379 } } ], "vout": [ { "amount": 1706480501, "target": { "key": "c9d7a126d4bf1aecd02232b9aef3bed6103ab03e9d804b107c41859057bb14b1" } } ], "extra": [ 1, 67, 111, 10, 211, 148, 248, 186, 133, 186, 27, 93, 26, 24, 234, 60, 107, 164, 93, 231, 68, 75, 210, 148, 226, 231, 5, 117, 52, 10, 132, 22, 221, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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