Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0dc2dad5d253572126f644ec329ae80adfa7d8a0402934dfd6f683386d00b593

Tx prefix hash: 47f0c7a1659be1842d5eac6c7e547d1853092882d9d5b53e3ce8285fedf7a668
Tx public key: d6edbf8df25c96767057d175772a80e8835ecf96a37e55df1679a6410bb35ecb
Timestamp: 1681987532 Timestamp [UCT]: 2023-04-20 10:45:32 Age [y:d:h:m:s]: 01:268:00:10:59
Block: 742659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 453037 RingCT/type: yes/0
Extra: 01d6edbf8df25c96767057d175772a80e8835ecf96a37e55df1679a6410bb35ecb02110000000575e3f0e9000000000000000000

1 output(s) for total of 2.124528955000 dcy

stealth address amount amount idx
00: 679e80996613de8009697b12ef1b2e2df6da51b9fcf43a3b0807803e2a45771f 2.124528955000 1189636 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": 742669, "vin": [ { "gen": { "height": 742659 } } ], "vout": [ { "amount": 2124528955, "target": { "key": "679e80996613de8009697b12ef1b2e2df6da51b9fcf43a3b0807803e2a45771f" } } ], "extra": [ 1, 214, 237, 191, 141, 242, 92, 150, 118, 112, 87, 209, 117, 119, 42, 128, 232, 131, 94, 207, 150, 163, 126, 85, 223, 22, 121, 166, 65, 11, 179, 94, 203, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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