Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50ab9945eaf001c775e969c67828c6e1660595bcef1d2dbd097662c1751b60b4

Tx prefix hash: bb7b7dfd7d107dbdf2031e04e9e09dc90da809cf7f5482f0218efebf5edb652b
Tx public key: 45e929dac16ba6588f5d98d7941bb051dd1ff85b265ec2f5faaed3f0fed9f809
Timestamp: 1702358818 Timestamp [UCT]: 2023-12-12 05:26:58 Age [y:d:h:m:s]: 01:345:08:42:33
Block: 911300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 505695 RingCT/type: yes/0
Extra: 0145e929dac16ba6588f5d98d7941bb051dd1ff85b265ec2f5faaed3f0fed9f809021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0e5e9fed412ad6668dca442dc020fcf9a3f3aa14a58a702fc172ebfe7107da6 0.600000000000 1368481 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": 911310, "vin": [ { "gen": { "height": 911300 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0e5e9fed412ad6668dca442dc020fcf9a3f3aa14a58a702fc172ebfe7107da6" } } ], "extra": [ 1, 69, 233, 41, 218, 193, 107, 166, 88, 143, 93, 152, 215, 148, 27, 176, 81, 221, 31, 248, 91, 38, 94, 194, 245, 250, 174, 211, 240, 254, 217, 248, 9, 2, 17, 0, 0, 0, 7, 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