Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8022c9d7357d1ae10ccf9f893d8564729be2de1daa36a1f56ee4b88d0a0b7ad

Tx prefix hash: cc5cc929fcfa06e475bb99945ed7ed85f94d84d49d766dd7dbcf1eb962088e4f
Tx public key: dd94c84b597ca928fe6f13ff3d933ba2701d6165e6df35c93c7431c1d07718f5
Timestamp: 1645105847 Timestamp [UCT]: 2022-02-17 13:50:47 Age [y:d:h:m:s]: 02:314:10:35:01
Block: 440516 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 744120 RingCT/type: yes/0
Extra: 01dd94c84b597ca928fe6f13ff3d933ba2701d6165e6df35c93c7431c1d07718f5021100000023bf7ee4e7000000000000000000

1 output(s) for total of 21.300407781000 dcy

stealth address amount amount idx
00: 81ac8093e1f502aead4cc891fbb2fbe81299f573e6668d79c6db8d7cd89a1276 21.300407781000 852881 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": 440526, "vin": [ { "gen": { "height": 440516 } } ], "vout": [ { "amount": 21300407781, "target": { "key": "81ac8093e1f502aead4cc891fbb2fbe81299f573e6668d79c6db8d7cd89a1276" } } ], "extra": [ 1, 221, 148, 200, 75, 89, 124, 169, 40, 254, 111, 19, 255, 61, 147, 59, 162, 112, 29, 97, 101, 230, 223, 53, 201, 60, 116, 49, 193, 208, 119, 24, 245, 2, 17, 0, 0, 0, 35, 191, 126, 228, 231, 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