Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f708e464b3f5502f0b53ad401bf6b52b04917acb7242e2b10bc9a4be175cac1

Tx prefix hash: 2f1a66da5a9ec87e7982e1f85b05b21ebc4bd854cb5883387d1c6bd76e2bf080
Tx public key: 532622511605857bc86ae981bc0378c915a291e1890479a64f7a8a352e594c33
Timestamp: 1582292741 Timestamp [UCT]: 2020-02-21 13:45:41 Age [y:d:h:m:s]: 05:022:17:09:46
Block: 69532 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1169418 RingCT/type: yes/0
Extra: 01532622511605857bc86ae981bc0378c915a291e1890479a64f7a8a352e594c3302110000000112c4732d000000000000000000

1 output(s) for total of 361.103484912000 dcy

stealth address amount amount idx
00: 494598c423cd4a7549ada565f2c5e01ea89974d85571dadd7a25015bb9b2471a 361.103484912000 128252 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": 69542, "vin": [ { "gen": { "height": 69532 } } ], "vout": [ { "amount": 361103484912, "target": { "key": "494598c423cd4a7549ada565f2c5e01ea89974d85571dadd7a25015bb9b2471a" } } ], "extra": [ 1, 83, 38, 34, 81, 22, 5, 133, 123, 200, 106, 233, 129, 188, 3, 120, 201, 21, 162, 145, 225, 137, 4, 121, 166, 79, 122, 138, 53, 46, 89, 76, 51, 2, 17, 0, 0, 0, 1, 18, 196, 115, 45, 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