Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 694b18763f3f0cf82f6a9804f9737ac6f1374e0ec59c0b3088b4f47c58780454

Tx prefix hash: 00b57cf950a1ce72c59d0a880adaca4f6b0a25e614919fc1cd27cff5a6b8fde7
Tx public key: a4f005ecc55aa45d6e1909cd329a0ceabfdde8b02522e3a632d0f47000ca2d40
Timestamp: 1717940705 Timestamp [UCT]: 2024-06-09 13:45:05 Age [y:d:h:m:s]: 00:358:10:24:42
Block: 1040481 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256202 RingCT/type: yes/0
Extra: 01a4f005ecc55aa45d6e1909cd329a0ceabfdde8b02522e3a632d0f47000ca2d400211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fbd13c25821ced265cecbefe4682699b7bdb82fca9ec2e0cc7b0a8bceca51a03 0.600000000000 1509138 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": 1040491, "vin": [ { "gen": { "height": 1040481 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fbd13c25821ced265cecbefe4682699b7bdb82fca9ec2e0cc7b0a8bceca51a03" } } ], "extra": [ 1, 164, 240, 5, 236, 197, 90, 164, 93, 110, 25, 9, 205, 50, 154, 12, 234, 191, 221, 232, 176, 37, 34, 227, 166, 50, 208, 244, 112, 0, 202, 45, 64, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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