Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 979441ceb82aa8384117182bd796b43a206b53b444300b79bae15db862e2d4a2

Tx prefix hash: 27d4599ff740a4221cd1ba8931444f7e1ee2e1a9b16fdbf4b5ef066668457bde
Tx public key: ea90cddb6215cbd791e5ccf66a76baceafa3eb4c246e221bf8800e96754a9df7
Timestamp: 1583894425 Timestamp [UCT]: 2020-03-11 02:40:25 Age [y:d:h:m:s]: 04:326:22:47:32
Block: 80232 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1128508 RingCT/type: yes/0
Extra: 01ea90cddb6215cbd791e5ccf66a76baceafa3eb4c246e221bf8800e96754a9df702110000000178e4872e000000000000000000

1 output(s) for total of 332.781264562000 dcy

stealth address amount amount idx
00: d69500c848fe699aa1e58f20cb5acff5ad4f63ef33f63cdcbe1a11145f73f072 332.781264562000 146822 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": 80242, "vin": [ { "gen": { "height": 80232 } } ], "vout": [ { "amount": 332781264562, "target": { "key": "d69500c848fe699aa1e58f20cb5acff5ad4f63ef33f63cdcbe1a11145f73f072" } } ], "extra": [ 1, 234, 144, 205, 219, 98, 21, 203, 215, 145, 229, 204, 246, 106, 118, 186, 206, 175, 163, 235, 76, 36, 110, 34, 27, 248, 128, 14, 150, 117, 74, 157, 247, 2, 17, 0, 0, 0, 1, 120, 228, 135, 46, 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