Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a4fca53842f5099107f5ed64405f2632c28554ce5cbdab15c26e5b45acf0208

Tx prefix hash: 86d012a7dc62a268c69a66fc3ed6d9aac8db206bd3c5a142d8c8c79d12fcd184
Tx public key: 2ed70866b1591d071441155e4d82e27cab59356edfb9b80c2a0b36fa68ac670f
Timestamp: 1672850617 Timestamp [UCT]: 2023-01-04 16:43:37 Age [y:d:h:m:s]: 02:090:08:48:57
Block: 667536 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 586257 RingCT/type: yes/0
Extra: 012ed70866b1591d071441155e4d82e27cab59356edfb9b80c2a0b36fa68ac670f02110000000252542ceb000000000000000000

1 output(s) for total of 3.768565652000 dcy

stealth address amount amount idx
00: 26e406ef6a300a089fd3076af49673ff89979a2a5ebca3e4ea6c8b4540e039f4 3.768565652000 1108749 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": 667546, "vin": [ { "gen": { "height": 667536 } } ], "vout": [ { "amount": 3768565652, "target": { "key": "26e406ef6a300a089fd3076af49673ff89979a2a5ebca3e4ea6c8b4540e039f4" } } ], "extra": [ 1, 46, 215, 8, 102, 177, 89, 29, 7, 20, 65, 21, 94, 77, 130, 226, 124, 171, 89, 53, 110, 223, 185, 184, 12, 42, 11, 54, 250, 104, 172, 103, 15, 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