Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e72a0ebd688965053bf9cba7c2f31a74528f4b30aa896825a335cfccb38f6e9

Tx prefix hash: f405e46a8b636dac546458590bed3a8068a529e1c5b5b7601f5571ea018fa915
Tx public key: 39a51827b87ff43959aa9cd38c0776a3d6e9748c68369c414734dafcb5721747
Timestamp: 1577919195 Timestamp [UCT]: 2020-01-01 22:53:15 Age [y:d:h:m:s]: 05:001:16:12:57
Block: 36681 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1151272 RingCT/type: yes/0
Extra: 0139a51827b87ff43959aa9cd38c0776a3d6e9748c68369c414734dafcb5721747021100000021ed383139000000000000000000

1 output(s) for total of 463.939630739000 dcy

stealth address amount amount idx
00: 0e21f70d78ef4fa28b10497c230a724ab6a7d30cdd1bdefa4d1d473e095287b6 463.939630739000 62189 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": 36691, "vin": [ { "gen": { "height": 36681 } } ], "vout": [ { "amount": 463939630739, "target": { "key": "0e21f70d78ef4fa28b10497c230a724ab6a7d30cdd1bdefa4d1d473e095287b6" } } ], "extra": [ 1, 57, 165, 24, 39, 184, 127, 244, 57, 89, 170, 156, 211, 140, 7, 118, 163, 214, 233, 116, 140, 104, 54, 156, 65, 71, 52, 218, 252, 181, 114, 23, 71, 2, 17, 0, 0, 0, 33, 237, 56, 49, 57, 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