Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a23dd131889bca3c643f7f717d4804929cafa276b787c196b736b5667b9adfcd

Tx prefix hash: 0b7ff9a49b1d3f1f081107c0369449ee2503af60c7b1e6e257cc4519e3275131
Tx public key: 37aa8107eb3a90e8e137109ef4e17b1acf1ab95264e2222ae6d2a4f16a226c87
Timestamp: 1580556422 Timestamp [UCT]: 2020-02-01 11:27:02 Age [y:d:h:m:s]: 05:075:19:06:42
Block: 56402 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1206128 RingCT/type: yes/0
Extra: 0137aa8107eb3a90e8e137109ef4e17b1acf1ab95264e2222ae6d2a4f16a226c870211000000024ac5aa02000000000000000000

1 output(s) for total of 399.132951867000 dcy

stealth address amount amount idx
00: 5d36e96951a6f898bfe5778b4c2753e2aa2dfb0e5b483812c55a259a5bfaa894 399.132951867000 104069 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": 56412, "vin": [ { "gen": { "height": 56402 } } ], "vout": [ { "amount": 399132951867, "target": { "key": "5d36e96951a6f898bfe5778b4c2753e2aa2dfb0e5b483812c55a259a5bfaa894" } } ], "extra": [ 1, 55, 170, 129, 7, 235, 58, 144, 232, 225, 55, 16, 158, 244, 225, 123, 26, 207, 26, 185, 82, 100, 226, 34, 42, 230, 210, 164, 241, 106, 34, 108, 135, 2, 17, 0, 0, 0, 2, 74, 197, 170, 2, 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