Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b581e0c636b8723865ad09631a3c6c42d223149f8b6f6f211845c4beade69a4

Tx prefix hash: bdfe3e2b533bd535d9d5f0c1ad2ad574d10b383bc102bd73ae8946f8eb8af484
Tx public key: 1ca179fda4fcba7e64585bf091451b1b20af75b8f6872bd1959a0d6bf972a11f
Timestamp: 1704268878 Timestamp [UCT]: 2024-01-03 08:01:18 Age [y:d:h:m:s]: 01:016:18:58:45
Block: 927130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273298 RingCT/type: yes/0
Extra: 011ca179fda4fcba7e64585bf091451b1b20af75b8f6872bd1959a0d6bf972a11f0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf26c301bf21e462c9725e0f10e4457d9664abc7983a089c48cc5828478d9489 0.600000000000 1384934 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": 927140, "vin": [ { "gen": { "height": 927130 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf26c301bf21e462c9725e0f10e4457d9664abc7983a089c48cc5828478d9489" } } ], "extra": [ 1, 28, 161, 121, 253, 164, 252, 186, 126, 100, 88, 91, 240, 145, 69, 27, 27, 32, 175, 117, 184, 246, 135, 43, 209, 149, 154, 13, 107, 249, 114, 161, 31, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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