Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c6bbcbad753202245c1460d412c095ddf6c4dc844a116ca0bb259c099de0891

Tx prefix hash: 4433a44485d375799cb9c0c4bfe3a5bb45b9dfbdd2339716edd2c58452097394
Tx public key: 979175ecf89620a47c744681451f6ed1053f9fa0b89356c09d0e547f4b4adba8
Timestamp: 1581294883 Timestamp [UCT]: 2020-02-10 00:34:43 Age [y:d:h:m:s]: 05:069:17:25:13
Block: 61719 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1202586 RingCT/type: yes/0
Extra: 01979175ecf89620a47c744681451f6ed1053f9fa0b89356c09d0e547f4b4adba8021100000001fe8cc51f000000000000000000

1 output(s) for total of 383.265871043000 dcy

stealth address amount amount idx
00: 066db46569baea7396848e12266b1ceb21a84f22a7f88a8845f1a28f7582b6fb 383.265871043000 113806 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": 61729, "vin": [ { "gen": { "height": 61719 } } ], "vout": [ { "amount": 383265871043, "target": { "key": "066db46569baea7396848e12266b1ceb21a84f22a7f88a8845f1a28f7582b6fb" } } ], "extra": [ 1, 151, 145, 117, 236, 248, 150, 32, 164, 124, 116, 70, 129, 69, 31, 110, 209, 5, 63, 159, 160, 184, 147, 86, 192, 157, 14, 84, 127, 75, 74, 219, 168, 2, 17, 0, 0, 0, 1, 254, 140, 197, 31, 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