Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6e155f74f6d01d93a116340189b5faddbe2d17b3659f757ba49fa49c87603aa

Tx prefix hash: a49a3e2a77bdd9608d07f212d77617c7fba9e5bbe3dcceea922f2db4ad8e02c9
Tx public key: a2231cbeed81dbec1b3df6b2c0eee4e2f900f0de0e4a05263495d8761e1c2194
Timestamp: 1673132790 Timestamp [UCT]: 2023-01-07 23:06:30 Age [y:d:h:m:s]: 02:101:12:39:56
Block: 669867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 594255 RingCT/type: yes/0
Extra: 01a2231cbeed81dbec1b3df6b2c0eee4e2f900f0de0e4a05263495d8761e1c219402110000000252542ceb000000000000000000

1 output(s) for total of 3.702137216000 dcy

stealth address amount amount idx
00: a06bfb2dbea05a7c497260a48d33d8b5bab156d20ad320a00cb544407e30a79a 3.702137216000 1111232 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": 669877, "vin": [ { "gen": { "height": 669867 } } ], "vout": [ { "amount": 3702137216, "target": { "key": "a06bfb2dbea05a7c497260a48d33d8b5bab156d20ad320a00cb544407e30a79a" } } ], "extra": [ 1, 162, 35, 28, 190, 237, 129, 219, 236, 27, 61, 246, 178, 192, 238, 228, 226, 249, 0, 240, 222, 14, 74, 5, 38, 52, 149, 216, 118, 30, 28, 33, 148, 2, 17, 0, 0, 0, 2, 82, 84, 44, 235, 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