Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ccdb46cfe93996df6754a27bc44097ba4335694870064557c4d123b609d83ea8

Tx prefix hash: f6e33b2a2a749c44b412f2326bab74907bae572fc1dea85fdb4d7b26a974ea43
Tx public key: f7cef79f9978d2a15bf8780ab00dd59caef44a8677e5961cb54e4bbee7ff92ce
Timestamp: 1682594250 Timestamp [UCT]: 2023-04-27 11:17:30 Age [y:d:h:m:s]: 02:033:06:45:12
Block: 747692 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 545948 RingCT/type: yes/0
Extra: 01f7cef79f9978d2a15bf8780ab00dd59caef44a8677e5961cb54e4bbee7ff92ce02110000000233af99f4000000000000000000

1 output(s) for total of 2.044495829000 dcy

stealth address amount amount idx
00: 4ae1ca7dcb6ae22ad6381c4a5e7cb47f0a9a7f9c1246d397ca0c80574ff0f753 2.044495829000 1195431 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": 747702, "vin": [ { "gen": { "height": 747692 } } ], "vout": [ { "amount": 2044495829, "target": { "key": "4ae1ca7dcb6ae22ad6381c4a5e7cb47f0a9a7f9c1246d397ca0c80574ff0f753" } } ], "extra": [ 1, 247, 206, 247, 159, 153, 120, 210, 161, 91, 248, 120, 10, 176, 13, 213, 156, 174, 244, 74, 134, 119, 229, 150, 28, 181, 78, 75, 190, 231, 255, 146, 206, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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