Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3adc2389dbc432280652773e8a417f33984893ef48b09bb501d519f5e4f704ab

Tx prefix hash: 1a56b2e7a663372ace86f6a85d968dd2f4281b3f2920029b7cf1bab0f6b383c2
Tx public key: ec246d025584298715f1179a9864d8ea4d369eb70c9158ae6445205a5e74b5db
Timestamp: 1708915614 Timestamp [UCT]: 2024-02-26 02:46:54 Age [y:d:h:m:s]: 01:112:16:58:24
Block: 965667 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341485 RingCT/type: yes/0
Extra: 01ec246d025584298715f1179a9864d8ea4d369eb70c9158ae6445205a5e74b5db02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9dbb6e41b93c728e2f011a6ec0d8176b95c454b91781c98a4638c2fe5270d4a5 0.600000000000 1425422 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": 965677, "vin": [ { "gen": { "height": 965667 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9dbb6e41b93c728e2f011a6ec0d8176b95c454b91781c98a4638c2fe5270d4a5" } } ], "extra": [ 1, 236, 36, 109, 2, 85, 132, 41, 135, 21, 241, 23, 154, 152, 100, 216, 234, 77, 54, 158, 183, 12, 145, 88, 174, 100, 69, 32, 90, 94, 116, 181, 219, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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