Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e314f6cdf55b33f8a32db960d212aac58a323069520844a7aa0fe35e45543939

Tx prefix hash: da05a06ee4a3cda9e2c50b22953182edab8a512524c36f4eadebb5b1323555d4
Tx public key: 168418f07b68a3ea2699e0ebbc1839fba6857f0cc11f6fe2f5f527005fd7077e
Timestamp: 1714493769 Timestamp [UCT]: 2024-04-30 16:16:09 Age [y:d:h:m:s]: 01:192:16:49:34
Block: 1011903 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396358 RingCT/type: yes/0
Extra: 01168418f07b68a3ea2699e0ebbc1839fba6857f0cc11f6fe2f5f527005fd7077e02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 406deaf66168e7fb35321192803fba7f18cfc0145a59cc35a5a58b17af236e28 0.600000000000 1474261 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": 1011913, "vin": [ { "gen": { "height": 1011903 } } ], "vout": [ { "amount": 600000000, "target": { "key": "406deaf66168e7fb35321192803fba7f18cfc0145a59cc35a5a58b17af236e28" } } ], "extra": [ 1, 22, 132, 24, 240, 123, 104, 163, 234, 38, 153, 224, 235, 188, 24, 57, 251, 166, 133, 127, 12, 193, 31, 111, 226, 245, 245, 39, 0, 95, 215, 7, 126, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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