Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d884f0229d6361740904d8bac5081d6d895be3434a52e951110ab847c35d2d0d

Tx prefix hash: 93118e35c7d8e853eb36fd8f67fa2a5de4b45d87baf8c60bdf53d695bc1ef770
Tx public key: 5bfe45462d80f8b941f42848c0a1692510c340820b2aa501e60ee1be657b8856
Timestamp: 1702079564 Timestamp [UCT]: 2023-12-08 23:52:44 Age [y:d:h:m:s]: 01:342:19:05:32
Block: 908983 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 503871 RingCT/type: yes/0
Extra: 015bfe45462d80f8b941f42848c0a1692510c340820b2aa501e60ee1be657b8856021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8717717b9950d1c355b60dc68b87ecd0328d24a5bdf630d8a2cbd0ba6c40c05 0.600000000000 1366048 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": 908993, "vin": [ { "gen": { "height": 908983 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8717717b9950d1c355b60dc68b87ecd0328d24a5bdf630d8a2cbd0ba6c40c05" } } ], "extra": [ 1, 91, 254, 69, 70, 45, 128, 248, 185, 65, 244, 40, 72, 192, 161, 105, 37, 16, 195, 64, 130, 11, 42, 165, 1, 230, 14, 225, 190, 101, 123, 136, 86, 2, 17, 0, 0, 0, 2, 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