Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 879591835574c571a5ac10ff73a3da25f9c2eb470b8f62d657ee4a27e86031d4

Tx prefix hash: bcaf64f64010b66e549eab8891f8657fa4d3dafc32c773c87beca2c744603e53
Tx public key: 5917a2014318a4ce5e7d184e28540f98a74a4a51f005a66e1a01e7097ee86ff2
Timestamp: 1673962544 Timestamp [UCT]: 2023-01-17 13:35:44 Age [y:d:h:m:s]: 01:302:13:29:41
Block: 676742 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 477213 RingCT/type: yes/0
Extra: 015917a2014318a4ce5e7d184e28540f98a74a4a51f005a66e1a01e7097ee86ff20211000000068b7b6602000000000000000000

1 output(s) for total of 3.512956503000 dcy

stealth address amount amount idx
00: 0e7a1059ff4d33c1c518436c51517a94ca42d9a0139bbe297115227d8dd1d267 3.512956503000 1118469 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": 676752, "vin": [ { "gen": { "height": 676742 } } ], "vout": [ { "amount": 3512956503, "target": { "key": "0e7a1059ff4d33c1c518436c51517a94ca42d9a0139bbe297115227d8dd1d267" } } ], "extra": [ 1, 89, 23, 162, 1, 67, 24, 164, 206, 94, 125, 24, 78, 40, 84, 15, 152, 167, 74, 74, 81, 240, 5, 166, 110, 26, 1, 231, 9, 126, 232, 111, 242, 2, 17, 0, 0, 0, 6, 139, 123, 102, 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