Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30ebcf9d78497b2143e948e44d706ef9fb2dce43c61246770a972c13fb9fd09f

Tx prefix hash: d9e86579ce6fd105ccb7bb41ae2a48fd6414148706af85096aebea52f09ed649
Tx public key: 357e2e11b57de9b1770d56966779412df148411a3abdf17d81957c3f981f501f
Timestamp: 1724994929 Timestamp [UCT]: 2024-08-30 05:15:29 Age [y:d:h:m:s]: 00:236:14:16:25
Block: 1098959 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168968 RingCT/type: yes/0
Extra: 01357e2e11b57de9b1770d56966779412df148411a3abdf17d81957c3f981f501f02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4f25c1e2630969d575c0db0b7a20d946092bf1d1aa83f691dbaeb5ecb7abac1 0.600000000000 1574856 of 15

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": 1098969, "vin": [ { "gen": { "height": 1098959 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4f25c1e2630969d575c0db0b7a20d946092bf1d1aa83f691dbaeb5ecb7abac1" } } ], "extra": [ 1, 53, 126, 46, 17, 181, 125, 233, 177, 119, 13, 86, 150, 103, 121, 65, 45, 241, 72, 65, 26, 58, 189, 241, 125, 129, 149, 124, 63, 152, 31, 80, 31, 2, 17, 0, 0, 0, 1, 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