Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abc1d52ae58477551d068dd349fd834a6e423f92c94c22d26b1362791b6145ee

Tx prefix hash: 658d1bd8a6f5ca6ba623157a23b8706560e9dde2c8a084dcf580b86e3a2b326c
Tx public key: b11e5ce399f27cdfc74bdd6e7d8069f815f5712183f8e849a5a5e5c26fe626bd
Timestamp: 1724926821 Timestamp [UCT]: 2024-08-29 10:20:21 Age [y:d:h:m:s]: 00:087:15:11:55
Block: 1098400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62671 RingCT/type: yes/0
Extra: 01b11e5ce399f27cdfc74bdd6e7d8069f815f5712183f8e849a5a5e5c26fe626bd02110000000691e13c04000000000000000000

1 output(s) for total of 0.607980000000 dcy

stealth address amount amount idx
00: 9fb3ac9e85c982654a0ffb4622af94e7ac2ddcb0cdca4c940ff925e0ccf874ca 0.607980000000 1574101 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": 1098410, "vin": [ { "gen": { "height": 1098400 } } ], "vout": [ { "amount": 607980000, "target": { "key": "9fb3ac9e85c982654a0ffb4622af94e7ac2ddcb0cdca4c940ff925e0ccf874ca" } } ], "extra": [ 1, 177, 30, 92, 227, 153, 242, 124, 223, 199, 75, 221, 110, 125, 128, 105, 248, 21, 245, 113, 33, 131, 248, 232, 73, 165, 165, 229, 194, 111, 230, 38, 189, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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