Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff9c39a4344dffc9343645d48ee0efa781d9805425f4aa83184ef1c0a5b85a86

Tx prefix hash: bee1cdedd1620a6f0ff306ae337ac23c54db83f6b3c54732372f5a1d3a6cbe64
Tx public key: 7f2bec22d793229ee6430ded3f48530150bab1f18ccd51250a5270e1e7c0a6b1
Timestamp: 1577634569 Timestamp [UCT]: 2019-12-29 15:49:29 Age [y:d:h:m:s]: 05:043:10:20:34
Block: 34407 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1180798 RingCT/type: yes/0
Extra: 017f2bec22d793229ee6430ded3f48530150bab1f18ccd51250a5270e1e7c0a6b10211000000124943cd9f000000000000000000

1 output(s) for total of 472.058891034000 dcy

stealth address amount amount idx
00: cd115204b7fd4040d926b3c2c1194c783e523bea861353a1dd2281212d75541b 472.058891034000 57909 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": 34417, "vin": [ { "gen": { "height": 34407 } } ], "vout": [ { "amount": 472058891034, "target": { "key": "cd115204b7fd4040d926b3c2c1194c783e523bea861353a1dd2281212d75541b" } } ], "extra": [ 1, 127, 43, 236, 34, 215, 147, 34, 158, 230, 67, 13, 237, 63, 72, 83, 1, 80, 186, 177, 241, 140, 205, 81, 37, 10, 82, 112, 225, 231, 192, 166, 177, 2, 17, 0, 0, 0, 18, 73, 67, 205, 159, 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