Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c051c8020fac351c2616789c5cc3ad53acf94de864648e7163728fcf029a0bc

Tx prefix hash: 3dea5ea099eaca58e6f9e6b409184f49ee4a3d118948008406e41e3acb55f93b
Tx public key: 45c0e0eab9e988695e036ab5ea71e2709e3856057e3bad8403137d16ea866a0d
Timestamp: 1713153847 Timestamp [UCT]: 2024-04-15 04:04:07 Age [y:d:h:m:s]: 01:020:12:29:28
Block: 1000774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275654 RingCT/type: yes/0
Extra: 0145c0e0eab9e988695e036ab5ea71e2709e3856057e3bad8403137d16ea866a0d021100000003679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1972f8c1f7f5ad027420fa17b0a9f3d2f8fe98b9db0f3517b897bdc403555d1f 0.600000000000 1461274 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": 1000784, "vin": [ { "gen": { "height": 1000774 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1972f8c1f7f5ad027420fa17b0a9f3d2f8fe98b9db0f3517b897bdc403555d1f" } } ], "extra": [ 1, 69, 192, 224, 234, 185, 233, 136, 105, 94, 3, 106, 181, 234, 113, 226, 112, 158, 56, 86, 5, 126, 59, 173, 132, 3, 19, 125, 22, 234, 134, 106, 13, 2, 17, 0, 0, 0, 3, 103, 154, 138, 129, 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