Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4ff8d2b4a02cec3f9425e5559e1da5e2ebb604bc11d1024380031645988be1d

Tx prefix hash: 009ccc2bca1bbad776058f301539d4586623aa5acddc7a2ad9a95b5df17adb34
Tx public key: 396d527cf664b59ded4b2c379a3ec10696f5a25953d74f134b402086d916584b
Timestamp: 1583905331 Timestamp [UCT]: 2020-03-11 05:42:11 Age [y:d:h:m:s]: 05:000:18:37:17
Block: 80288 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1156322 RingCT/type: yes/0
Extra: 01396d527cf664b59ded4b2c379a3ec10696f5a25953d74f134b402086d916584b02110000001e8a2ee0d9000000000000000000

1 output(s) for total of 332.644854893000 dcy

stealth address amount amount idx
00: 312be345cb7f6a654d99534ff7e26a57274a41edad8778d56e6a46c1edce79e1 332.644854893000 146966 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": 80298, "vin": [ { "gen": { "height": 80288 } } ], "vout": [ { "amount": 332644854893, "target": { "key": "312be345cb7f6a654d99534ff7e26a57274a41edad8778d56e6a46c1edce79e1" } } ], "extra": [ 1, 57, 109, 82, 124, 246, 100, 181, 157, 237, 75, 44, 55, 154, 62, 193, 6, 150, 245, 162, 89, 83, 215, 79, 19, 75, 64, 32, 134, 217, 22, 88, 75, 2, 17, 0, 0, 0, 30, 138, 46, 224, 217, 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