Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4750eda70f668f7d69f9a17d81e818e97da8877d9269239aaa2865fed9db1d4

Tx prefix hash: 39dc67f9818ad40b55c5bf3bc9600e1f2796983fca01c53988452e4032759c1f
Tx public key: df8338b328494fb03345cb51ad11ed5e6a4d55ea52550bfa1bb35e75eb95b662
Timestamp: 1579047963 Timestamp [UCT]: 2020-01-15 00:26:03 Age [y:d:h:m:s]: 04:317:10:07:55
Block: 45683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1116374 RingCT/type: yes/0
Extra: 01df8338b328494fb03345cb51ad11ed5e6a4d55ea52550bfa1bb35e75eb95b66202110000000e4ac5aa02000000000000000000

1 output(s) for total of 433.145788804000 dcy

stealth address amount amount idx
00: 43c7ae00d172e9fcdef0ad52176b0a2dfc86147cde4ed00ae6452174cb9ca3f8 433.145788804000 83605 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": 45693, "vin": [ { "gen": { "height": 45683 } } ], "vout": [ { "amount": 433145788804, "target": { "key": "43c7ae00d172e9fcdef0ad52176b0a2dfc86147cde4ed00ae6452174cb9ca3f8" } } ], "extra": [ 1, 223, 131, 56, 179, 40, 73, 79, 176, 51, 69, 203, 81, 173, 17, 237, 94, 106, 77, 85, 234, 82, 85, 11, 250, 27, 179, 94, 117, 235, 149, 182, 98, 2, 17, 0, 0, 0, 14, 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